home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
mbbstd62.zip
/
DISK2.ZIP
/
GALMSG.ZIP
/
BBSRIP.MSG
< prev
next >
Wrap
Text File
|
1994-05-11
|
53KB
|
1,180 lines
LANGUAGE {English/ANSI},{English/RIP}
LEVEL3 {}
Users who have this key will never be forced to download
your custom library at logon or logoff. If you set the
LEVEL 4 options ODONACTN and ODOFACTN to FORCE, the BBS
will treat users who have this key as if ODONACTN and
ODOFACTN were set to CHOOSE. This also applies to users
who have either the MASTER key or who have the key
specified in option SYSKEY. (If ODONACTN or ODOFACTN are
set to WARN, then users with this key will only get a
warning message, like all other users).
BYPSKY {SYSOP} S 15 Key required to bypass forced downloads
LEVEL4 {}
When RIP is auto-sensed, the BBS will find out what version
of RIP the user calling in supports. If the user calling
in doesn't have at least this version, he'll be warned that
he needs to download an update.
This version code must be a 6 digit string without any
periods (like 015200 for version 1.52.00).
MINVER {015200} S 6 Minimum RIP version code for auto-sensing
When the BBS generates an automatic RIP menu, it displays a
button for each option specified for a menu page in the
menu tree - on your BBS's main system menu, this includes
the option to log off. Since RIP menus, by default, have a
Global Command Bar (contained in the text block DFSEND) at
the bottom, which has an "EXIT" button, displaying an
additional button for logging off may be redundant. Set
this option to NO to suppress the display of this button -
your users will use the "EXIT" button to log off your
system. Set this option to YES if you would like a button
displayed for the logoff option.
DSPXIT {Display button for exit from main menu? NO} B
To avoid displaying a button for the option to log off the
system, the BBS needs to know what module page calls the
module "Logoff (End Session)". Most often this is the
"EXIT" module page, but if you've changed that page name,
you should enter the new name here.
XITPGE {EXIT} (DSPXIT=NO) S 16 Name of "Logoff (End Session)" page
When automatically generating a RIP menu, the BBS uses
either of two different button and text style combinations:
a button and text style for larger buttons (specified in
the text blocks ENALGE and DIMLGE) or a button and text
style for smaller buttons (specified in the text blocks
ENASML and DIMSML). This option tells the BBS the maximum
number of options a menu can have and still be displayed
using the styles for larger buttons. If a menu has more
options than specified here, the BBS will display those
options using the styles for smaller buttons instead. Set
this option to 25 to always use the larger styles. Set
this option to 0 to always use the smaller styles.
MAXLGE {Maximum number of selections for large button style 16} N 0 25
For those users who are logged on with RIP, you may not
want the BBS to display any menu files which have
extensions of .IBM, .ANS, or .ASC. If you set this option
to NO, then when a RIP user is on a menu page, and that
menu page is set to display a file, the BBS will only look
for a menu file with a .RIP extension, and will ignore any
other files. If it can't find a file with a .RIP
extension, it will display an auto-generated menu. If you
set this option to YES, then the BBS will try each
extension in turn, as normal.
DSPOEXT {Display other menu file extensions for RIP users? NO} B
If you maintain a particular library of RIP icons and/or
scenes that are required for your BBS, you can have the BBS
check your users' hard drives for a certain file, compare
its date, time and size to a copy of that same file on the
BBS's hard drive and, if they're different, either force
the user to download your custom library, let the user
choose whether or not to download, or just warn the user
that their library is out of date. You can have the BBS
perform this check when a user logs on, when they log off,
or at both logon and logoff. Set this option to NO if your
BBS doesn't require any special icons and/or RIP scenes.
HASCLB {Does this BBS have a custom icon library? NO} B
This is the name (and, if you wish, the path) of the
signature file, on the BBS's hard drive, for your BBS's
library of icons and/or scenes. Whenever the BBS does a
remote check of this same file on a user's hard drive, it
will compare the date and time information it receives back
from the user's system to the date and time of this file.
A copy of the file specified here should be included with
your custom library - that is, placed in the same directory
specified in CLBPTH, or archived into the file specified in
ARCSPC (or both), along with the files which make up your
BBS's custom library.
SGNNAM {BBSRIP.ICN} (HASCLB=YES) S 39 Signature file name
This option tells the BBS whether you have all of your
custom icons and/or RIP scenes stored separately in a
directory on your hard drive, whether you've archived them
into a single file, or whether you have the library stored
both ways. When the download begins, if this option is set
to MULT, then the BBS will look in the directory specified
in CLBPTH and begin a download of all the files it finds
there. If this is set to ARCHVD, then the BBS will
download the file specified in ARCSPC. If this option is
set to BOTH, the user will be allowed to choose how they
want to download. All downloads will be via ZMODEM.
CLBFRM {How is the custom library stored? MULT} (HASCLB=YES) E MULT ARCHVD BOTH
If you set CLBFRM to either MULT or BOTH, this option tells
the BBS the directory path where the files for your custom
library are stored. If you specify an invalid directory
here, and CLBFRM is set to BOTH, then the BBS will download
the file specified in ARCSPC. If the directory is invalid
and CLBFRM is set to MULT, then the BBS will only warn the
user.
CLBPTH {CUSTLIB} (CLBFRM=MULT,BOTH) S 39 Custom library path
If you set CLBFRM to either ARCHVD or BOTH, this option
tells the BBS the name (and, if you wish, the path) of the
single archive file which contains the custom library. If
the file specified here doesn't exist, and CLBFRM is set to
BOTH, then the BBS will download the files it finds in the
directory specified in CLBPTH. If the file doesn't exist
and CLBFRM is set to ARCHVD, then the BBS will only warn
the user.
ARCSPC {CUSTLIB.ZIP} (CLBFRM=ARCHVD,BOTH) S 39 Custom archive name
This tells the BBS when to check for an out of date library
on the user's hard drive. You can have the BBS perform
this check at logon (after the user has entered their
User-ID and password), at logoff, or both. Note that if
you have this option set to BOTH, and the user does in fact
download at logon (and doesn't subsequently delete the
signature file!), then nothing will happen at logoff.
CHKSGN {When to check user's hard drive for signature file LOGON} (HASCLB=YES) E LOGON LOGOFF BOTH
This tells the BBS what action to take at logon if it
determines the user's library is out of date. If you set
this option to FORCE, then the user will receive a warning
message, and the download will begin after they hit ENTER.
If you set this to CHOOSE, a warning message will be sent,
but the user will be allowed to bypass the download if
they wish. If you set this to WARN, then the BBS will only
send a warning message, and no download will take place.
ODONACTN {Action at logon for out of date library FORCE} (CHKSGN=LOGON,BOTH) E FORCE CHOOSE WARN
This tells the BBS what action to take at logoff if it
determines the user's library is out of date. If you set
this option to FORCE, then the user will receive a warning
message, and the download will begin after they hit ENTER.
If you set this to CHOOSE, a warning message will be sent,
but the user will be allowed to bypass the download if
they wish. If you set this to WARN, then the BBS will only
send a warning message, and no download will take place.
ODOFACTN {Action at logoff for out of date library FORCE} (CHKSGN=